Converting spreadsheet applications to web-based applications

ABSTRACT

A networked version of a spreadsheet application can be automatically created from an existing “conventional” spreadsheet. In one implementation, a server may obtain a data file, where the data file represents a networked version of a spreadsheet application that was converted from the “conventional” application and the data file defines characteristics of the networked version of the spreadsheet application including logic and interactivity attributes of cells in the networked version of the spreadsheet application. A remote request may be received from a client to access the networked version of the spreadsheet application. In response, the server may transmit a document to the client that represents a portion of the networked version of the spreadsheet application that the interactivity attributes specify as being displayable to the client.

RELATED APPLICATIONS

This application claims priority from U.S. provisional patentapplication Ser. No. 60/629,577, filed Nov. 19, 2004, entitled “Systemand Method for Converting Spreadsheet Applications to Web-BasedApplications,” the contents of which are hereby incorporated byreference.

BACKGROUND

A. Field of the Invention

The present disclosure relates generally to spreadsheet applications,and more specifically, to converting spreadsheet applications toweb-based spreadsheet applications.

B. Description of the Related Art

Electronic spreadsheets are in widespread use in various industriesincluding finance, business and academia. One of the reasons for theirpopularity is that spreadsheets greatly facilitate implementation ofanalytical and/or database applications. However, spreadsheets canpresent problems when they are distributed or when they are large files.

Distribution of spreadsheets often results in loss of control over thespreadsheets. For example, the receiver of the spreadsheet can easilymodify it and redistribute the modified spreadsheet withoutauthorization by the distributor. In addition, the receiver may be ableto access proprietary data and/or formulas that the creator may not wishto give to the receiver. Although there are security measures availablewithin current spreadsheet programs such as password protection, theycan be defeated. Furthermore, spreadsheets of large size can also createproblems when using them. Specifically, spreadsheets can be so largethat having multiple spreadsheets active on one computer taxes resourcesof the computer, increasing the possibility of a computer crash.

SUMMARY

One aspect is directed to a method that may include receiving aspreadsheet application designed to execute using a first spreadsheetprogram and converting the spreadsheet application into a data file. Thedata file defines characteristics of a networked version of thespreadsheet application. The characteristics may include informationdefining cells of the networked version of the spreadsheet applicationthat are to be displayable to a user of the networked version of thespreadsheet application. The method further includes transmitting thedata file to a server to make the data file available to network usersas the networked version of the spreadsheet application.

Another aspect is directed to a method that may include obtaining a datafile, the data file representing a networked version of a spreadsheetapplication that was converted from a first spreadsheet application andthe data file defining characteristics of the networked version of thespreadsheet application including logic and interactivity attributes ofcells in the networked version of the spreadsheet. The method furtherincludes receiving a remote request from a client to access thenetworked version of the spreadsheet application and transmitting, inresponse to the request, a document to the client that represents aportion of the networked version of the spreadsheet application that theinteractivity attributes specify as being displayable to the client.

Yet another aspect includes a method for converting a spreadsheetapplication to a web-based application. The method includes receiving anextensible markup language (XML) document that was created based on thespreadsheet application, creating a computer program based on the XMLdocument, receiving a request for a display screen of the web-basedapplication from a client, constructing a document for displaying thedisplay screen, and transmitting the document for displaying the displayscreen to the client.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate an embodiment of the inventionand, together with the description, explain the invention. In thedrawings,

FIG. 1 is a diagram of an exemplary system in which concepts consistentwith the principles of the invention may be implemented;

FIG. 2 is a block diagram illustrating an exemplary implementation ofthe computing devices shown in FIG. 1 in additional detail;

FIG. 3 is a diagram illustrating an exemplary logic file created by theconverter computer shown in FIG. 2;

FIGS. 4A-4D are diagrams illustrating an exemplary IO file created bythe converter computer shown in FIG. 2;

FIG. 5 is a diagram of an exemplary spreadsheet application that may beconverted to create the logic files shown in FIGS. 3 and 4A-4D;

FIGS. 6A and 6B are diagrams illustrating exemplary abstract syntaxtrees (ASTs); and

FIGS. 7A-7D are flow charts illustrating exemplary operation of thesystem shown in FIG. 1 in converting a spreadsheet application to aweb-based application.

DETAILED DESCRIPTION

The following detailed description of the invention refers to theaccompanying drawings. The detailed description does not limit theinvention.

Overview

Implementations consistent with the principles of the invention relateto converting a spreadsheet application to a web-based spreadsheetapplication. The web-based spreadsheet application may exhibitsubstantially the same appearance and logic as the spreadsheetapplication. In one implementation, the conversion may be performedusing extensible markup language (XML).

System Description

FIG. 1 is a diagram of an exemplary system 100 in which conceptsconsistent with the principles of the invention may be implemented.System 100 may include users 110 and 112, computers 122 and 124, aserver 130, and network 140. User 110 will be described herein as a“user converter” that initiates conversion of a spreadsheet applicationto a web-based application using “converting” computer 122. Users 112will be described herein as “user viewers” that may view and interactwith the converted web-based application using “viewing” computers 124.One of ordinary skill in the art will recognize that more generally, asingle user 110, 112 or computer 122, 124 can function as either or bothof a converting user/computer or a viewing user/computer.

Network 140 may include the Internet, an intranet, a wireless network orother types of network alone or in combination. Server 130 may includeone or more computing devices designed to interact or serve data tocomputers 122 and 124. Server 130 and computers 122 and 124 will bedescribed in more detail below. It should be noted that although asingle computer 122, two computers 124, a single network 140, and asingle server 130 are shown in FIG. 1, in many practicalimplementations, a typical system 100 may include more of thesecomponents.

FIG. 2 is a block diagram illustrating an exemplary implementation ofcomputers 122, 124 and server 130 in additional detail.

Converting Computer 122

As shown in FIG. 2, converting computer 122 includes spreadsheetapplication 210, processor 220, XML document 230, one or more picturefiles 240, and web browser 260. Processor 220 may include one or moreprocessors that are used to execute the software programs, such asspreadsheet application 210 and web browser 260, that are executing atcomputer 122. Computer 122 may run a web browsing program such as webbrowser 260 that is capable of displaying a web page 262.

Spreadsheet application 210 may be a conventional spreadsheetapplication designed to execute and be used locally on a computer.Spreadsheet application 210 may be organized into a number of viewablesections, such as, for example, a main workbook 212 and one or moreassociated workbooks 212 a. Each workbook 212, 212 a may include one ormore worksheets 214. Each worksheet 214, in turn, may include one ormore cells 216. Cells 216 may be designated by user converter 110 asdisplay cells 216 a or smart cells 216 c. Display cells 216 a, in turn,may be designated by user converter 110 as to whether the cells areeditable cells, shown as editable cells 216 b. User converter 110 may,for instance, designate all display cells 216 a as editable cells 216 bor designate all cells 216 as display cells 216 a.

Consistent with an aspect of the invention, spreadsheet application 210may include an analytical application to assist in converting thespreadsheet to a web-based version of the spreadsheet. For example,spreadsheet application 210 may include the Microsoft Excel™ spreadsheetprogram, available from Microsoft Corporation, augmented with an add-onprogram to perform the conversion of Excel spreadsheets to a web-basedspreadsheet 270. Other spreadsheet programs, such as the OpenOffice.org“Calc” spreadsheet program, may alternatively be used instead ofMicrosoft Excel™. Spreadsheet application 210 may also include orinteract with other applications such as a database application or amodeling application.

Main workbook 212 may be used by user converter 110 to initiate aprocess to convert spreadsheet application 210 to web-based spreadsheet270. Associated workbooks 212 a may be workbooks that are referred to informulas in main workbook 212. Display cells 216 a may be cells 216 thatuser converter 110 designates as cells that are to be displayed to userviewer 112 in web-based application 270. Editable cells 216 b may bedisplay cells 216 a that user converter 110 designates as cells whosecontent user viewer 112 may modify in web-based application 270. Smartcells 216 c may be cells 216 that user converter 110 designates as cellsthat act as a data interface between web-based application 270 and otherapplications, such as user tracking applications or DLLs (dynamic linklibraries). Smart cells 216 c may use an interface such as the SOAP(simple XML-based protocol) interface to exchange data.

Each cell 216 may include logic, such as a constant, a formula, or otherinputs permitted by spreadsheet application 210. In addition, each cell216 may include one or more interactivity attributes that define waysthat cell 216 interacts with the user, including how cell 216 isdisplayed to the user and how the user may modify the cell. Suchattributes may comprise cell height, cell width, cell color, acceptablenumber input range, acceptable input format, dropdown lists, or otherattributes that the spreadsheet application 210 uses to define the waycell 216 looks or how it may be manipulated by its user.

Converting computer 122 may collect logic information from each cell 216and interactivity attribute information from each display cell 216 a andconvert that information into XML, resulting in XML document 230. XMLdocument 230 may therefore include logic of cells 216 and interactivityattributes of display cells 216 a within spreadsheet application 210.XML document 230 can be generally conceptualized as a data file thatacts as an intermediary version of the spreadsheet application.

XML document 230 may include a logic file 234 and an input/output file(IO file) 232. An exemplary logic file 234 is shown in FIG. 3 and anexemplary 10 file 232 is shown in FIGS. 4A-4D. Logic file 234 and IOfile 232 are derived from the conversion of spreadsheet application 212.An exemplary spreadsheet application 210 that may be converted to obtainlogic file 234 and IO file 232 is shown in FIG. 5.

Logic file 234 may include information regarding logic of each cell 216,including information regarding location of smart cells 216 c. IO file232 may include information regarding interactivity attributes of eachdisplay cell 216 a, including information regarding location of editablecells 216 b. In addition, IO file 232 may include information regardingcharts located within ranges of display cells 216 a so that charts canbe recreated in web-based application 270. Such chart informationpreferably includes chart name, type of chart, sources of data series,colors of the chart, legend information, etc. It should be noted thatbecause IO file 232 may collect interactivity attribute information fromdisplay cells 216 a, including editable cells 216 b, IO file 232 mayinclude interactivity attribute information of only those parts ofworkbooks 212, 212 a that user converter 110 wants displayed to userviewer 112 in the converted web-based spreadsheet application 270.Accordingly, user converter 110 is able to easily “hide” any selectedportions of the spreadsheet from user viewer 112.

In one implementation, logic in spreadsheet application 210 may beabbreviated when constructing logic file 234. For example, if adjacentcells 216 contain similar logic, these cells may be grouped together inlogic file 234 to describe their logic as a group rather than describingthe logic of each cell individually. This concept is illustrated insection 310 of FIG. 3. In another implementation consistent with aspectsof the invention, interactivity attribute information may be abbreviatedfor display cells 216 a when constructing I/O file 232. For example, ifadjacent display cells 216 a contain similar interactivity attributes,these cells may be grouped together in I/O file 232 to describe theirinteractivity attributes as a group rather than describing interactivityof each cell individually.

Images in spreadsheet application 212 may be processed to obtain picturefile(s) 240. Picture file(s) 240 may be referenced as an embedded objectin IO file 232 to indicate the name of picture file(s) 240.

Viewing Computer 124 and Server 130

XML file 230 and picture file 240 together contain information necessaryto implement the web-based version of spreadsheet application 210. Asshown in FIG. 2, XML file 230 and picture file 240 may be uploaded toserver 130. Server 130 may implement computer program 250 to constructcomputer program objects according to information in XML document 230.Additionally, computer program 250 may work in conjunction with webbrowser 260 on viewing computer 124 to implement web-based application270.

Server 130 may include XML document 230, one or more picture files 240and computer program 250. Computer program 250, in turn, may includethree components: engine component 252, spreadsheet applicationcomponent 254 and data component 256. Computer program 250 and webbrowser 260 can be used to implement web-based application 270.

Engine component 252 of computer program 250 may convert XML document230 into computer program objects. The objects may include spreadsheetapplication component 254 and data component 256, which togethercomprise interactivity attributes of display cells 216 a and logic ofcells 216. Using spreadsheet application component 254 and datacomponent 256, engine component 252 directs data flow and calculationswithin computer program 250.

More specifically, web-based application 270 may be implemented byengine component 252 constructing abstract syntax trees (ASTs) usinglogic contained within spreadsheet application component 254 and datacomponent 256. Each node of the ASTs may include a constant, a function,or a pointer depending on logic of spreadsheet application component 254and/or data component 256. Engine component 252 may construct only thoseASTs necessary to display calculation results in display cells 216 a.Therefore, if there is logic contained in spreadsheet applicationcomponent 254 or data component 256 that does not affect display cells216 a, engine component 254 may not construct ASTs corresponding to thatlogic. Engine component 252 preferably places the constructed ASTs inspreadsheet application component 254. Engine component 252 mayconstruct new ASTs when user viewer 112 enters new data within web page262 if the new data requires new ASTs for engine component 252 toperform calculations for displaying display cells 216 a.

FIGS. 6A and 6B are diagrams illustrating exemplary ASTs. In FIG. 6A,four cells 601-604 are shown. Cells 601-603 each include a constantvalue and the AST for these cells is simply a single node containing theconstant value of the cell. Cell 604, however, includes a function thatreferences constants and other cells.

FIG. 6B is a diagram illustrating the AST for cell 604 in additionaldetail. Top level node 610 defines the function (“IF”) of cell 604.Nodes 620 define the three sub-functions of the function in node 610.Namely, an equals function, a plus function, and another IF function.Nodes 630 relate to the functions defined by nodes 620. For the equalsfunction, for instance, nodes 630 include the two arguments for thefunction: a pointer to the value in cell “C” (cell 603) and theconstant 1. Similarly, for the plus function, nodes 630 define the twoarguments as pointers to the values in cells “A” (cell 601) and “B”(cell 602). The IF function in nodes 620 is defined similarly to the IFfunction in node 610. That is, it includes three lower level nodeswithin nodes 630 (and any nodes dependent on these nodes).

Returning to FIG. 2, in one implementation, engine component 252 iswritten in JAVA and spreadsheet application component 254 and datacomponent 256 include JAVA objects. It should be noted that enginecomponent 252 may not change with different spreadsheets, butspreadsheet application component 254 and data component 256 can varywith different spreadsheet, since they are dependent on XML document230. This type of software architecture is advantageous in that problemswithin computer program 250 are confined to spreadsheet applicationcomponent 254 or data component 256 since engine component 252 isalready known to operate properly.

Furthermore, computer program 250 may be designed to allow enginecomponent 252 to simultaneously run multiple web-based applications 270.This is possible since web-based-application-specific information isconfined to spreadsheet application components 254 and data component256 objects. Engine component 252 may be capable of managing more thanone set of spreadsheet application component 254 and data component 256that correspond to different web-based applications 270.

User viewers 112 may view and interact with web-based application 270using web browser 260. For example, computer program 250 may transmitHTML to web browser 260 which, in turn, displays web page 262 that mayhave substantially the same look and feel of corresponding portions ofspreadsheet application 210. Therefore, web-based application 270presents substantially the same look and feel of corresponding portionsof spreadsheet application 210 as well as substantially the same logicas spreadsheet application 210.

One difference between spreadsheet application 210 and web-basedapplication 270 is that user viewers 112 are not able to manually modifyvalues within display cells 216 a unless they are designated as editablecells 216 b by user converter 110. Display cells 216 a that are noteditable cells 216 b may be altered only by computer program 250according to logic in spreadsheet application component 254 and/or datacomponent 256.

If a user viewer 112 modifies or enters new data in editable cells 216 bin web page 262 and requests a recalculation of web-based application270, web browser 260 preferably transmits HTML of web page 262,including the new data, to computer program 250. Engine component 252may then perform calculations with the new data using ASTs. Computerprogram 250 may construct new ASTs as required for calculations.Computer program 250 may then construct a new HTML page based on theresults of the calculations. The new HTML page is transmitted tocomputer 124, where web browser 260 displays new web page 262. It shouldbe noted that other types of markup language such as XML may betransmitted by computer program 250 to web browser 260.

In an alternative embodiment of the present invention, web-basedapplication 270 may be set to an on-the-fly calculation mode. In thismode, as content of an editable cell is altered by user viewer 112, webbrowser 260 sends that piece of modified content to computer program 250rather than the entire HTML of web page 262. This may be performed byincluding an event in the HTML that responds to any changes to the webpage 262. In an another implementation, web browser 260 can be set toperiodically send modified HTML to computer program 250 automatically.Engine component 252 performs calculations using ASTs, constructing newASTs as necessary to complete the calculations. Then, rather thantransmitting the entire set of HTML, computer program 250 transmits onlythe necessary HTML to web page 260 that modifies portions of web page262 to reflect the new data and calculation results. In still anotherpossible implementation, the user creator may decide that the entirespreadsheet application be converted to HTML instead of specifyingcertain sections.

The interaction between user viewer 112, web browser 260, web page 262and computer program 250 may be carried out multiple times. In this way,web browser 260, web page 262 and computer program 250 work together asweb-based application 270 that includes substantially the sameappearance and logic as spreadsheet application 210 but with someuser-application interactivity defined by user converter 110.

The operation of system 100 in converting a spreadsheet application to aweb-based application will be described in more detail with reference tothe flow charts of FIGS. 7A-7D. Display cells 216 a may be defined inworkbooks 212 and 212 a at converting computer 122 (act 702). This maybe done by defining ranges or by highlighting specific cells inworkbooks 212 and 212 a.

Cells within display cells 216 a are initially determined that should bedesignated as editable cells 216 b (act 704). As previously mentioned,an editable cell is one that allows user viewer 112 to modify or enternew data in the cell when interacting with web-based application 270.Cells that are likely to be editable cells may be inferred from thelayout of the spreadsheet. User converter 110 may then be prompted tomanually designate any additional editable cells 216 b within displaycells 216 a (act 706). In response, if desired, user converter 110 maydesignate additional editable cells 216 b (act 708). User converter 110may be prompted to designate smart cells 216 c so that computer program250 is capable of exchanging data with other applications (act 710).User converter 110 may designate the smart cells 216 c (act 712). Insome implementations, smart cells 216 c may be automatically determined.

Workbooks 212 a that are associated with the main workbook 212 may beidentified (act 714). As described above, main workbook 212 isassociated with other workbooks 212 a if main workbook 212 containsformulas that refer directly or indirectly to other workbooks. Formulaspreferably can refer indirectly to other workbooks by referring to anentry in a workbook that, in turn, refers to another workbook. If any ofassociated workbooks 212 a are open, the open associated workbook(s) 212a are included for conversion with their current values (acts 716 and718). If an associated workbook 212 a is not open, these associatedworkbooks 212 a with last available values are included for conversion(acts 716 and 720).

In acts 722-736, logic information is collected from cells 216 andconverted into XML, resulting in logic file 234 of XML document 230. Theworkbooks that are to be converted may be identified and enumerated (act722). Worksheets 214 within these workbooks are also identified (act724). For each workbook 212, 212 a and each worksheet 214 withinworkbook 212, 212 a, constants may be identified and inventoried withinlogic file 234 (act 726). For each workbook 212, 212 a and eachworksheet 214 within workbook 212, 212 a, formulas may be identified andinventoried within logic file 234 (act 728).

For workbook 212, 212 a and each worksheet 214 within workbook 212, 212a, named formulas, named ranges, queries and smart cells 216 c may berespectively identified and inventoried (acts 730-736). Named formulasare formulas within workbooks 212, 212 a that have assigned names.Similarly, named ranges may include groups of cells 216 withinspreadsheet application 210 that have assigned names. Queries may becapable of obtaining data from outside of spreadsheet application 210and placing the data within spreadsheet application 210. In oneimplementation, the data queried may reside in server 130 or isavailable in other servers.

In acts 738-750, interactivity attribute information from display cells216 a may be collected and converted into XML, resulting in IO file 232of XML document 230. In some implementations, IO file 232 may be mergedwith or included as a part of logic file 234. Unique style formattingattributes of display cells 216 a may be identified and enumerated in IOfile 232 (act 738). A style formatting attribute may be determined byattributes such as font-family, font-size, color, background,text-align, vertical-align, width and height, etc. Unique number formatattributes of display cells 216 a may be identified and enumerated in IOfile 232 (act 740). Unique script type attribute of editable cells 216 bmay be identified and enumerated in IO file 232 (act 742). Existingborder attributes of display cells 216 a may also be identified andenumerated in IO file 232 (act 744). A border attribute may includeborder-style, border-color and border-width.

Existing group names in workbooks 212, 212 a may also be identified andinventoried in IO file 232 (act 746). Group names may include namesassigned to ranges of display cells 216 a by user converter 110 so thateach group represents a single web page 262 in web-based application270. Each display cell 216 a may be inventoried to obtain the enumeratedstyle formatting, number format, script type, and border type attributesof display cells 216 a (act 748). This information may be stored in IOfile 232. Hyperlinks within display cells 216 a may be identified andinventoried (act 750). The hyperlinks may point to, for example,additional external web pages or to other sections of the spreadsheet.This information may be stored in IO file 232. Embedded objects withinranges of display cells 216 a may also be identified and inventoried(act 752). This information may be stored in IO file 232. For embeddedobjects that are charts linked with data in spreadsheet application 210,converting computer 122 may indicate in IO file 232 chart attributessuch as chart type, source data series, legend information and otherinformation necessary to recreate the chart in web-based application270. For embedded objects that are images, converting computer 122 mayconvert that object into one or more picture files 240 and indicatenames of picture files 240 as embedded objects in IO file 232.

After assembling XML document 230 and picture files 240, as describedabove, converting computer 122 may transmit XML document 230 and picturefiles 240 (if any) to computer program 250 of server 130 (act 754). Aspreviously described, engine component 252 of computer program 250constructs spreadsheet application component 254 and data component 256based on information within XML document 230 (act 756). If smart cellsexist, engine component 252 may construct data interfaces in spreadsheetapplication component 254 with which computer program 250 may exchangedata with other applications residing in server 130 or other serversnetworked with server 130 (act 758).

A URL may be assigned to the web-based spreadsheet created byspreadsheet application component 254 and data component 256 (act 760).Server 130 may receive a request for the web-based spreadsheet from userviewer 112 via the URL (act 762). In response, engine component 252 mayconstruct the ASTs necessary to calculate entries in display cells 216 ausing logic information contained in spreadsheet application component254 and data component 256, and place the ASTs in spreadsheetapplication component 254 (act 764). Using the constructed ASTs, enginecomponent 252 may then perform the calculations dictated by thespreadsheet (act 766). The calculations performed in act 766 may includeall or substantially all of the calculations defined in the originalspreadsheet, including numerical analysis functions and database accessfunctions. Some of the calculations may be particularly suited to anetworked environment. For example, the spreadsheet may include afiltering function that allows the user to limit the data shown bysetting criteria in a data field, such as, for example, limiting a“date” field to only shown entries after a certain date.

The resultant version of the spreadsheet, including the calculatedresults and interactivity attribute information, may then be convertedinto an HTML document that displays display cells 216 a (act 768). TheHTML document may include links to any images in picture file 240 (act770). The HTML document may then be transmitted to web browser 260,which, in turn, may display the HTML document as web page 262 to theviewer user 112 (acts 772 and 774). Web page 262 may include links toexternal items, such as images in picture file 240 from server 130. Webbrowser 260 may resolve these links and display the images as part ofweb page 262.

User viewer 112 may enter new data or modify existing data contained indisplay cells 216 a when the display cells are designated as editablecells 216 b (act 776). Web browser 260 may then transmit the new ormodified data to computer program 250 (act 778). Engine component 252may then construct new ASTs as necessary for calculations, includinglogic of smart cells 216 c (act 780). Engine component 252 may thenperform calculations according to the new ASTs (act 782). The updatedversion of the spreadsheet may be converted into HTML and transmittedback to viewer user 112 (acts 784 and 786). Acts 776-786 may be repeatedeach time the user modifies the web-based spreadsheet (act 788).

CONCLUSION

As described above, a web-based spreadsheet application can beautomatically created from an existing “conventional” spreadsheet. Theweb-based spreadsheet can be uploaded to a server and presented tousers. The web-based spreadsheet may provide a number of advantages overconventional spreadsheets. For example, formulas or other information ina spreadsheet that the spreadsheet author would like to hide from theviewer may reside only at the server and not be sent to the viewer, thusmaking it impossible for the viewer to learn this information.Additionally, because the calculations for the spreadsheet may beperformed at the server, complex or large spreadsheets may still bedisplayed at the viewing computer without overburdening the viewingcomputer.

The foregoing description of exemplary embodiments of the inventionprovides illustration and description, but are not intended to beexhaustive or to limit the invention to the precise form disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practice of the invention. Forexample, while a spreadsheet application was primarily described hereinas being created with a convention spreadsheet program, the spreadsheetapplication could itself have been directly created as an online orweb-based application.

For example, while a series of acts have been described with regard toFIGS. 7A-7D, the order of the acts may be varied in otherimplementations consistent with the invention. Moreover, non-dependentacts may be implemented in parallel.

It will also be apparent to one of ordinary skill in the art thataspects of the invention, as described above, may be implemented in manydifferent forms of software, firmware, and hardware in theimplementations illustrated in the figures. The actual software code orspecialized control hardware used to implement aspects consistent withthe principles of the invention is not limiting of the invention. Thus,the operation and behavior of the aspects of the invention weredescribed without reference to the specific software code—it beingunderstood that one of ordinary skill in the art would be able to designsoftware and control hardware to implement the aspects based on thedescription herein.

Further, certain portions of the invention may be implemented as “logic”or as a “component” that performs one or more functions. This logic orcomponent may include hardware, such as an application specificintegrated circuit or a field programmable gate array, software, or acombination of hardware and software.

No element, act, or instruction used in the description of the inventionshould be construed as critical or essential to the invention unlessexplicitly described as such. Also, as used herein, the article “a” isintended to include one or more items. Where only one item is intended,the term “one” or similar language is used. Further, the phrase “basedon” is intended to mean “based, at least in part, on” unless explicitlystated otherwise.

1. A method comprising: receiving a spreadsheet application designed toexecute using a spreadsheet program; converting the spreadsheetapplication into a data file, the data file defining characteristics ofa networked version of the spreadsheet application, the characteristicsincluding information defining cells of the networked version of thespreadsheet application that are to be displayable to a user of thenetworked version of the spreadsheet application; and transmitting thedata file to a server to make the data file available to network usersas the networked version of the spreadsheet application.
 2. The methodof claim 1, wherein the networked version of the spreadsheet applicationis a web-based version of the spreadsheet application.
 3. The method ofclaim 1, wherein the data file is an extensible markup language (XML)data file.
 4. The method of claim 1, wherein the data file furtherincludes information defining interactivity attributes of each of thedisplayable cells.
 5. The method of claim 4, wherein the informationregarding the interactivity attributes of the displayable cells isabbreviated.
 6. The method of claim 1, wherein the data file furtherincludes information defining logical functions implemented by cells inthe spreadsheet application.
 7. The method of claim 6, wherein thelogical functions include information defining formulas stored in thecells.
 8. The method of claim 6, wherein the logical functions includeinformation defining data filtering functions.
 9. The method of claim 6,wherein the logical functions include information defining a datainterface between the spreadsheet application and other applications.10. The method of claim 6, wherein the logical functions are abbreviatedin the data file.
 11. The method of claim 1, wherein the networkedversion of the spreadsheet application comprises substantially the samelogic as the spreadsheet application.
 12. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions which, when executed by aprocessor, cause the processor to: receive a spreadsheet applicationdesigned to execute using a spreadsheet program; convert the spreadsheetapplication into a data file, the data file defining characteristics ofa networked version of the spreadsheet application, the characteristicsincluding logic and interactive attributes of cells of the networkedversion of the spreadsheet application; and transmit the data file to aserver configured to make the data file available to network users asthe networked version of the spreadsheet application.
 13. Thecomputer-readable medium of claim 12, wherein the data file is anextensible markup language (XML) data file. 14-28. (canceled)
 29. Thecomputer-readable medium of claim 12, wherein the data file furtherincludes information defining interactivity attributes of each of thedisplayable cells, the information regarding the interactivityattributes of the displayable cells being abbreviated.
 30. Thecomputer-readable medium of claim 12, wherein the data file furtherincludes information defining logical functions implemented by cells inthe spreadsheet application, the logical functions including at leastone of: information defining formulas stored in the cells, informationdefining data filtering functions, or information defining a datainterface between the spreadsheet application and other applications.31. A device comprising: a memory to store instructions; and a processorto execute the instructions to: receive a spreadsheet applicationdesigned to execute using a spreadsheet program; convert the spreadsheetapplication into a data file, the data file defining characteristics ofa networked version of the spreadsheet application, the characteristicsincluding information defining cells of the networked version of thespreadsheet application that are to be displayable to a user of thenetworked version of the spreadsheet application; and transmit the datafile to a server to make the data file available to network users as thenetworked version of the spreadsheet application.
 32. A device of claim31, wherein the networked version of the spreadsheet application is aweb-based version of the spreadsheet application, and the data file isan extensible markup language (XML) data file.
 33. A device of claim 31,wherein the data file further includes information defininginteractivity attributes of each of the displayable cells, theinformation regarding the interactivity attributes of the displayablecells being abbreviated.
 34. A device of claim 31, wherein the data filefurther includes information defining logical functions implemented bycells in the spreadsheet application, the logical functions including atleast one of: information defining formulas stored in the cells,information defining data filtering functions, or information defining adata interface between the spreadsheet application and otherapplications.
 35. A device of claim 31, wherein the networked version ofthe spreadsheet application comprises substantially the same logic asthe spreadsheet application.